Nurse call system with wireless software updating

ABSTRACT

The present disclosure may be embodied as a nurse call system. The nurse call system may include a patient hub. The patient hub may include a nurse call interface circuit configured to be in electronic communication with a nurse call patient station. The patient hub may further include a hub controller in electronic communication with the nurse call interface circuit. The nurse call system may further include a patient interaction device (“PID”). The PID may include a hub interconnect configured to be in electronic communication with the hub controller. The PID may further include a wireless communication link for receiving a PID software update. The PID software update may be a PID firmware update. The PID software update may be a PID operating system update.

FIELD OF THE DISCLOSURE

The present disclosure is generally directed to nurse call systems foruse in hospital environments, and more particularly, to the wirelessupdating of electronic components of such nurse call systems.

BACKGROUND OF THE DISCLOSURE

Healthcare facilities, such as hospitals, are diverse settings offeringmany different types of care across many different wards. Care offeredat a facility may encompass general or acute, intensive, specialized,rehabilitative, long-term, pediatric, geriatric, psychiatric, and othervarieties of care. Different campuses, buildings within a campus, orwards within a building may be dedicated to providing each type of careto their corresponding patients.

Nurse call functionality is often an integral component of the diversecare settings and services offered. Whether the same nurse call systemis installed across an entire campus or building, or localized to aparticular ward or even newly-installed hospital wing, the healthcareservices provided alongside nurse call are often fractured across wards.For example, a ward dedicated to childbirth care may provide one set ofservices that differ from services provided in a ward dedicated tolong-term care and rehabilitation. Room environmental controls areanother type of service that may vary across wards or even rooms, assome rooms may offer “scenes,” for example, that set different lightingstyles as a form of complementary therapy.

Furthermore, patient engagement and education have increasingly becomeimportant services provided as part of an overall care experience.Material may be offered to inform the patient about the condition theyare being treated for and what to expect during the recovery process.Vital health data being monitored by the caregivers may be offered tothe patient so they understand and are engaged with the treatmentprocess. Many other innovative services exist, and new services continueto be developed and deployed to offer patients richer, morecomprehensive services.

Traditionally, pillow speaker systems providing nurse call and basicentertainment functions to the patient are deployed using commonhardware and fixed, static software. Different component part numbers(SKUs) may exist to offer different types of nurse call notifications,room environmental controls, entertainment functions, and compatibilitywith entertainment systems. Nevertheless, once deployed throughout ahospital setting, the pillow speaker and corresponding offered servicesremain static unless the unit is swapped out or reconfigured throughdirect, physical intervention.

As pillow speaker systems evolve into more comprehensive platformsoffering a variety of modern capabilities, such as improved audio,high-quality video display, internet connectivity, access to mobileapplications (“apps”), and custom apps tailored to complement the careservices, using a static software image is increasingly undesirable.

Accordingly, there is a critical need for pillow speaker systems capableof updating their software without direct, physical intervention.

BRIEF SUMMARY OF THE DISCLOSURE

In an aspect of the present disclosure, a nurse call system ispresented. The nurse call system may include a patient hub. The patienthub may include a nurse call interface circuit configured to be inelectronic communication with a nurse call patient station. The patienthub may further include a hub controller in electronic communicationwith the nurse call interface circuit. The nurse call system may furtherinclude a patient interaction device (“PID”). The PID may be a pillowspeaker. The PID may include a hub interconnect configured to be inelectronic communication with the hub controller. The PID may furtherinclude a wireless communication link for receiving a PID softwareupdate. The PID software update may be a PID firmware update. The PIDsoftware update may be a PID operating system update.

The PID may further include a PID memory unit. The PID may be configuredto load the PID software update into the PID memory unit. In oneembodiment, the PID may be configured to load the PID software updateinto the PID memory unit only if the PID software update has beenverified as genuine. The PID may further include a PID memory recoverymodule configured to load a previous PID software version into the PIDmemory unit if the PID software update fails to load.

The PID may be configured to produce a confirmation sound when the PIDsoftware update is successfully programmed into the PID memory unit. Theconfirmation sound may be produced by an audio speaker.

The PID may be configured to produce a confirmation notice when the PIDsoftware update is successfully programmed into the PID memory unit. Theconfirmation notice may be shown by a display screen.

The PID may be further configured to receive a hub software updatereceived via the wireless communication link. The PID may be furtherconfigured to transmit the hub software update to the hub controller viathe hub interconnect. The PID may be a pillow speaker. The hub softwareupdate may be a hub firmware update.

The hub controller may include a hub memory unit. The hub controller maybe configured to load the hub software update into the hub memory unit.In one embodiment, the hub controller may be configured to load the hubsoftware update into the hub memory unit only if the hub software updatehas been verified as genuine. The hub controller may further include ahub memory recovery module configured to load a previous hub softwareversion into the hub memory unit if the hub software update fails toload.

The PID may be configured to produce a confirmation sound when the hubsoftware update is successfully programmed into the hub memory unit. Theconfirmation sound may be produced by an audio speaker.

The PID may be configured to display a confirmation notice when the hubsoftware update is successfully programmed into the hub memory unit. Theconfirmation notice is shown by a display screen.

The PID may be further configured to receive a nurse call softwareupdate received via the wireless communication link. The PID may befurther configured to transmit the nurse call software update to the hubcontroller via the hub interconnect. The hub controller may beconfigured to transmit the nurse call software update to the nurse callinterface circuit via an intrahub communication link. The nurse callsoftware update may be a nurse call firmware update. The PID may be apillow speaker.

The nurse call interface circuit may include a nurse call memory unit.The nurse call interface circuit may be configured to load the nursecall software update into the nurse call memory unit. In one embodiment,the nurse call interface circuit may be configured to load the nursecall software update into the nurse call memory unit only if the nursecall software update has been verified as genuine. The nurse callinterface circuit may further include a nurse call memory recoverymodule configured to load a previous nurse call software version intothe nurse call memory unit if the nurse call software update fails toload.

The PID may be configured to produce a confirmation sound when the nursecall software update is successfully programmed into the nurse callmemory unit. The confirmation sound may be produced by an audio speaker.

The PID may be configured to display a confirmation notice when thenurse call software updated is successfully programmed into the nursecall memory unit. The confirmation notice may be shown by a displayscreen.

DESCRIPTION OF THE DRAWINGS

For a fuller understanding of the nature and objects of the disclosure,reference should be made to the following detailed description taken inconjunction with the accompanying drawings, in which:

FIG. 1 is an embodiment of a patient interface devices (“PID”);

FIG. 2 is an embodiment of a nurse call system with a PID, patient hub,nurse call patient station; and

FIG. 3 is a schematic of an embodiment of the nurse call system asdisclosed herein.

DETAILED DESCRIPTION OF THE DISCLOSURE

In an aspect of the present disclosure, a nurse call system 100 ispresented. The nurse call system 100 may include a patient hub 103. Thepatient hub 103 may include a nurse call interface circuit 106configured to be in electronic communication with a nurse call patientstation 109. The patient hub 103 may further include a hub controller112 in electronic communication with the nurse call interface circuit106. The nurse call system 100 may further include a patient interactiondevice (“PID”) 115. The PID 115 may be a pillow speaker. The PID 115 mayinclude a hub interconnect 118 configured to be in electroniccommunication with the hub controller 112. The PID 115 may furtherinclude a wireless communication link 121 for receiving a PID softwareupdate. The PID software update may be a PID firmware update. The PIDsoftware update may be a PID operating system (“OS”) update.

During manufacturing, a software client may be installed on the PID 115for Mobile Device Management (“MDM”) lifecycle maintenance via, forexample, a cloud service. The software client may be any MDM softwaresuch as, for example AirWatch by VMware. The software client may beconfigured to securely connect to and synchronize with the MDM servicethrough the Internet via, for example, the wireless communication link121. The software client may be registered and/or authorized to downloadand install one or more software programs and/or updates provided by theMDM service. By synchronizing with the MDM service, the software clientis able to determine the software programs, updates, configurationchanges, and/or other modifications available to download to, installon, and/or apply to the PID 115.

The software program, updates, changes, etc. on the MDM service may bemanaged by, for example, the PID manufacturer by way of a remoteconsole. For example, in the case of MDM provided as a cloud server, thePID manufacturer may access the service by logging into a web-basedadministrative interface over the Internet. From this interface, themanufacturer may upload software programs, updates, changes, etc., fordistribution to all or a selected subset of devices. The MDM may alsoenable remote review and/or management of the software client of eachPID 115 connected to the MDM service. Each PID 115 may be individuallymanaged. Additionally or alternatively, a number of PIDs 115 may bemanaged as a group. For example, a set of PIDs 115 used for similarapplications can be managed as a group. Software programs, updates,changes, etc., may be transmitted as a result of an affirmative actionby the manufacturer, or they may be transmitted automatically from anexternal source, such as, for example, a build server. To update an OSof the PID 115, rather than a user-level application, a bootloader orsimilar program may be running on the PID 115 to allow for the OS updateto be installed into a flash memory, a storage disk partition, etc., ofthe PID 115.

The PID 115 may further include a PID memory unit 124. The PID 115 maybe configured to load a PID software update into the PID memory unit124. In one embodiment, the PID 115 may be configured to load a PIDsoftware update into the PID memory unit 124 only if the PID softwareupdate has been verified as genuine. In an MDM embodiment in which thesoftware programs and/or updates are for user-level applications, theMDM software client may be responsible for verification. The softwareclient may be configured to connect with the MDM service in a securefashion. The software client may first download the software programsand/or updates into memory or into a temporary disk partition or folderin a file system, and then subsequently verify the download (e.g.,authenticate). In one example, this verification process may includechecking a software checksum or cryptographic hash function to confirmall of the downloaded bits match the expected software checksum or hash.

In an embodiment in which software updates comprise updates to the OS orfirmware of the PID 115, the use of public key cryptography may be used.In a particular example, the Rivest-Shamir-Adleman (“RSA”) algorithm maybe used, in which public/private key pairs are used to verify genuinesoftware updates. An illustrative example of verification follows.First, a public key(s) is programmed into a processor of the PID 115 ata permanent, non-volatile, location such as an electronic fuse. Anauthorized software developer remotely creates a software “image”including the new software updates and the software image iscryptographically signed with a private key. The private key may be, forexample, a one-way hash function calculated from the software image.Alternatively, the private key may be any other key generation algorithmas defined and supported by the RSA algorithm. The private key mayperform RSA encryption as the signature. The private key is known onlyto the authorized software developer. To perform the update andauthentication check, the PID may be configured to run bootloadersoftware. This bootloader software may be configured to receive theremote software update, as well as temporarily storing it in memory orin a disk partition. The bootloader then uses the preprogrammed publickey to verify the data bits of the software update as authentic,according to, for example, the RSA algorithm. The public key may performRSA decryption as verification. The bootloader software may verify thesoftware update either in real time as data packets are received, orafter receiving the full update. Although an illustrative example usingthe RSA algorithm is provided, this example is non-limiting and otherschemes may be used.

The PID 115 may further include a PID memory recovery module 127configured to load a previous PID software version into the PID memoryunit 124 if the PID software update fails to load. The PID softwareupdate may fail to load for a wide array of reasons. In one example, ifthe software update is transmitted by an MDM service over the Internet,the transmission may be interrupted by a lost Internet connection. TheInternet connection may be lost for a variety of reasons, such as, forexample, the MDM service becoming unavailable. Internet Service Provider(“ISP”) issues with the Internet connection between the MDM service andthe location of the PID 115, or congestion or failure of the hardwaresupporting the Internet connection, such as routers, switches, andmodems. In another example, the wireless communication link 121 may becorrupted by an electronically noisy environment, prohibiting sufficienttransmission data packets via the link. In another example, the wirelesscommunication link 121 may be interrupted due to the placement ofmaterial with electromagnetic shielding properties around the PID 115.In another example, the bootloader software facilitating the OS orfirmware update may become unresponsive, erratic, or even crash due tosoftware bugs, unhandled exceptions or conditions, or other externalevents interfering with the software updating routine. In anotherexample, hardware faults while transmitting data may cause a failure toload the PID software update.

The PID memory unit 124 may be divided into two or more partitions. Forexample, the PID memory unit 124 may be divided into a bootloaderpartition and an application partition. In a further example, the PIDsoftware update may only update one of the partitions, such as theapplication partition.

The PID 115 may be configured to produce a confirmation sound when thePID software update is successfully programmed into the PID memory unit124. The confirmation sound may be produced by an audio speaker 130.

The PID 115 may be configured to produce a confirmation notice when thePID software update is successfully programmed into the PID memory unit124. The confirmation notice may be shown by a display screen 133. Inanother embodiment, the one or more confirmation notices may bedisplayed while the software update is programming the PID memory unit124. For example, the confirmation notices may display at stages orintervals of the PID software update installation, such as 25%, 50%,75%, and 100% of completion.

The PID 115 may be further configured to receive a hub software updatereceived via the wireless communication link 121. For example, the hubsoftware update may be received in a similar manner to the PID softwareupdate described above. The PID 115 may be further configured totransmit the hub software update to the hub controller 112 via the hubinterconnect 118. The PID 115 may be a pillow speaker. The hub softwareupdate may be a hub firmware update.

The hub controller 112 may include a hub memory unit 139. The hubcontroller 112 may be configured to load the hub software update intothe hub memory unit 139. In one embodiment, the hub controller 112 maybe configured to load the hub software update into the hub memory unit139 only if the hub software update has been verified as genuine. Thehub software update may be, for example, verified in a similar manner tothe PID software update described above. The hub controller 112 mayfurther include a hub memory recovery module 142 configured to load aprevious hub software version into the hub memory unit 139 if the hubsoftware update fails to load. The hub memory unit 139 may be dividedinto two or more partitions. For example, the hub memory unit 139 may bedivided into a bootloader partition and an application partition. In afurther example, the hub software update may only update one of thepartitions, such as the application partition.

The PID 115 may be configured to produce a confirmation sound when thehub software update is successfully programmed into the hub memory unit139. The confirmation sound may be produced by an audio speaker 130.

The PID 115 may be configured to display a confirmation notice when thehub software update is successfully programmed into the hub memory unit139. The confirmation notice is shown by a display screen 133. Inanother embodiment, the one or more confirmation notices may bedisplayed while the software update is programming the hub memory unit139. For example, the confirmation notices may appear at stages orintervals of the hub software update installation, such as 25%, 50%,75%, and 100% of completion.

The PID 115 may be further configured to receive a nurse call softwareupdate received via the wireless communication link 121. The PID 115 maybe further configured to transmit the nurse call software update to thehub controller 112 via the hub interconnect 118. The hub controller 112may be configured to transmit the nurse call software update to thenurse call interface circuit 106 via an intrahub communication link 151.The nurse call software update may be a nurse call firmware update. ThePID 115 may be a pillow speaker.

The nurse call software update procedure may utilize bootloader softwareresiding on, for example, a nurse call interface circuit 106. Thisbootloader software is responsible for programming the nurse callsoftware update into a proper memory location (such as, for example,flash memory) to allow for execution after reboot. The bootloadersoftware may be an in-application programmer.

A primary difference between installing a nurse call software update, ahub software update, and a PID software update is the number of “hops”(or links) between devices within the nurse call system 100 required foreach respective software update to reach its destination. As a PIDsoftware update is initially received by the PID 115 from the wirelesscommunication link 121 and installed on the PID 115 itself, no “hops”are required. Regarding a hub controller software update, one “hop” isrequired to convey the update from the PID 115 to the hub controller112. Regarding a nurse call software update, two “hops” are required toconvey the update to the nurse call interface circuit 106; first, fromthe PID 115 to the hub controller 112 (hop one), and second, from thehub controller 112 to the nurse call interface circuit 106 (hop two).

As described above, the PID 115 may receive the update over the wirelesscommunication link 121. The PID 115 may have a software applicationinstalled capable of recognizing a nurse call software update has beendownloaded. In some embodiments, the PID 115 may be configured fortriggering (remotely or locally) to begin a nurse call software updateprocedure. This software application may then issue a command across acommunication channel to instruct the hub controller 112 to configurethe nurse call interface circuit 106 into bootloader or in-applicationprogrammer mode. The communication channel may be a custom or anycommonly-used communication channel. For example, the communicationchannel may be a Universal Serial Bus (“USB”) or serial UniversalAsynchronous Receiver-Transmitter (“UART”) link. The command may be inthe form of custom data packets. The PID 115 transmits the nurse callsoftware update data to the hub controller 112, which the hub controller112 then transmits to the bootloader of the nurse call interface circuit106 for programming into memory. This transmission of data continuesuntil the nurse call software update is fully programmed into memory.Once fully programmed, the PID 115, via the hub controller 112, mayissue a reset command to the nurse call interface circuit 106. The resetcommand reboots the nurse call interface circuit 106 for the nurse callsoftware update to load.

The nurse call interface circuit 106 may include a nurse call memoryunit 145. The nurse call interface circuit 106 may be configured to loadthe nurse call software update into the nurse call memory unit 145. Inone embodiment, the nurse call interface circuit 106 may be configuredto load the nurse call software update into the nurse call memory unit145 only if the nurse call software update has been verified as genuine.

Depending on the capabilities of the bootloader, the available hardwareand/or software peripherals (such as support for public keycryptography), and the available size of program memory, the bootloadermay verify the nurse call software update in a similar manner to the PIDsoftware update described above. The verification of the nurse callsoftware update may occur upstream in the PID 115 or hub controller 112,as well as in the nurse call interface circuit 106. Based on theavailable program memory size and capabilities of their associatedprocessors or microcontrollers, any of the three devices in the chainmay store the public key used to verify the nurse call software update.The verification may occur either “on-the-fly” or after the entireupdate is received by the device and stored in an available memorylocation. In the case of the nurse call interface circuit 106 performingthe verification, its memory may be allocated into “A” and “B”partitions. Both partitions may be large enough to store the nurse callsoftware update, meaning the total memory space of the nurse callinterface circuit is at least large enough to store two copies of thenurse call software update and the bootloader software. In one example,if the software update at memory location “A” is active (meaning itboots and runs when the nurse call interface circuit 106 is reset), thenthe software update is programmed to location “B”. When the softwareupdate in location “B” is cryptographically verified, a non-volatileflag, such as a bit stored in Electrically Erasable ProgrammableRead-Only Memory (“EEPROM”) or a flash memory location acting as anEEPROM, is set such that the bootloader knows to load the firmware atlocation B at next startup. Subsequently, location “A” is made availableto receive the next software update.

The nurse call interface circuit 106 may further include a nurse callmemory recovery module 148 configured to load a previous nurse callsoftware version into the nurse call memory unit 145 if the nurse callsoftware update fails to load.

The nurse call software update may fail to load for similar reasons asthe PID software update described above, except that the nurse callupdate must travel through additional hardware communication paths andmicrocontrollers. These paths and microcontrollers may be corrupted bynoise from electrostatic discharge (“ESD”) events, power loss,physically broken connectors, wires, and/or traces, and bugs in thesoftware update.

The nurse call memory unit 145 may be divided into two or morepartitions. For example, the nurse call memory unit 145 may be dividedinto a bootloader partition and an application partition. In a furtherexample, the nurse call software update may only update one of thepartitions, such as the application partition.

The PID 115 may be configured to produce a confirmation sound when thenurse call software update is successfully programmed into the nursecall memory unit 106. The confirmation sound may be produced by an audiospeaker 130.

The PID 115 may be configured to display a confirmation notice when thenurse call software update is successfully programmed into the nursecall memory unit 145. The confirmation notice may be shown by a displayscreen 133. In another embodiment, the one or more confirmation noticesmay be displayed while the software update is programming the nurse callmemory unit 145. For example, the confirmation notices may appear atstages or intervals of the nurse call software update installation, suchas 25%, 50%, 75%, and 100% completion.

Three examples of implementations of one or more of the embodiments ofthe disclosed nurse call system are provided below.

Example 1

Different varieties of advanced pillow speaker systems may comprisecommon hardware components to reduce the number of overall componentpart numbers (SKUs) required to manufacture the systems, and thereforereduce manufacturing cost by increasing the volume of production perSKU. However, it may be difficult, time consuming, error prone, costly,and/or entirely not possible to uniquely track each individual unit fromproduction at the factory to installation in a particular room. Instead,it is highly desirable to implement a system to uniquely identify andregister each unit at the factory. Once identified and registered, theunit may be installed in any room, and uniquely configured based on thecare services offered in that particular room. At the factory, theseunits may be identified using a serial number and registered withsoftware providing wireless, over-the-air (OTA) update capability. Atthe healthcare facility, the units may be identified in each room usingtheir hardware MAC address when connected to an intranet. Similarly, theMAC address may be paired with the serial number stored on the devicefor pairing to the OTA software when securely connected to the Internet.At this point, the OTA software may install the desired software imagedesigned for the room's care profile.

Example 2

In a second example, software updates are provided to pillow speakersystems that are already deployed when new features, improvements,and/or fixes to existing features are developed. In a traditional pillowspeaker implementation, this is a long and costly process, wherein apatient room must first be unoccupied, and a technician must physicallychange or reconfigure the old unit. This process must be repeatedroom-by-room. Software updating is inflexible in this implementation,and compelling features may not be deployed simply because it is toodifficult to update units. Using a wireless, OTA software updateimplementation, multiple rooms, entire wings or wards, or even largergroups of units may be automatically updated simultaneously as new orimproved features are available. It may even be possible to update theunit without vacating the room if a hospital protocol to provide such anupdate determines the risk is acceptable. The reduced difficulty andcost of updating units makes updates more flexible, which in turn maydrive greater adaptation of new and innovative patient care services.

Example 3

A third example involves patient turnover. Even in a case where asoftware image running on an advanced pillow speaker system isrelatively static for the room or ward it occupies (making the servicesit provides similarly static), there may be patient registration,configuration, personal health, or other data stored in or at leastprocessed by the unit. Wireless, OTA software updates may be used as atool to “wipe” the unit by erasing the unit's memory and reinstall thesoftware to restore it to default factory settings or baselinefunctional software in between sitting patients, thus ensuringconfidentiality of data from patient to patient.

Although the present disclosure has been described with respect to oneor more particular embodiments, it will be understood that otherembodiments of the present disclosure may be made without departing fromthe spirit and scope of the present disclosure. Hence, the presentdisclosure is deemed limited only by the appended claims and thereasonable interpretation thereof.

We claim:
 1. A nurse call system, comprising: a patient hub, comprising:a nurse call interface circuit configured to be in electroniccommunication with a nurse call patient station; and a hub controller inelectronic communication with the nurse call interface circuit; and apatient interaction device (“PID”), comprising: a hub interconnectconfigured to be in electronic communication with the hub controller;and a wireless communication link for receiving a PID software update.2. The nurse call system of claim 1, wherein the PID software update isa PID firmware update.
 3. The nurse call system of claim 1, wherein thePID software update is a PID operating system update.
 4. The nurse callsystem of claim 1, wherein the PID further comprises a PID memory unit,and the PID is configured to load the PID software update into the PIDmemory unit.
 5. The nurse call system of claim 4, wherein the PID isconfigured to load the PID software update into the PID memory unit onlyif the PID software update has been verified as genuine.
 6. The nursecall system of claim 4, wherein the PID further comprises a PID memoryrecovery module configured to load a previous PID software version intothe PID memory unit if the PID software update fails to load.
 7. Thenurse call system of claim 4, wherein the PID is configured to produce aconfirmation sound when the PID software update is successfullyprogrammed into the PID memory unit.
 8. The nurse call system of claim7, wherein the confirmation sound is produced by an audio speaker. 9.The nurse call system of claim 4, wherein the PID is configured toproduce a confirmation notice when the PID software update issuccessfully programmed into the PID memory unit.
 10. The nurse callsystem of claim 9, wherein the confirmation notice is shown by a displayscreen.
 11. The nurse call system of claim 1, wherein the PID is apillow speaker.
 12. The nurse call system of claim 1, wherein the PID isfurther configured to receive a hub software update received via thewireless communication link, and to transmit the hub software update tothe hub controller via the hub interconnect.
 13. The nurse call systemof claim 12, wherein the hub software update is a hub firmware update.14. The nurse call system of claim 12, wherein the hub controllercomprises a hub memory unit, and the hub controller is configured toload the hub software update into the hub memory unit.
 15. The nursecall system of claim 14, wherein the hub controller is configured toload the hub software update into the hub memory unit only if the hubsoftware update has been verified as genuine.
 16. The nurse call systemof claim 14, wherein the hub controller further comprises a hub memoryrecovery module configured to load a previous hub software version intothe hub memory unit if the hub software update fails to load.
 17. Thenurse call system of claim 14, wherein the PID is configured to producea confirmation sound when the hub software update is successfullyprogrammed into the hub memory unit.
 18. The nurse call system of claim17, wherein the confirmation sound is produced by an audio speaker. 19.The nurse call system of claim 14, wherein the PID is configured todisplay a confirmation notice when the hub software update issuccessfully programmed into the hub memory unit.
 20. The nurse callsystem of claim 19, wherein the confirmation notice is shown by adisplay screen.
 21. The nurse call system of claim 12, wherein the PIDis a pillow speaker.
 22. The nurse call system of claim 1, wherein thePID is further configured to receive a nurse call software updatereceived via the wireless communication link and to transmit the nursecall software update to the hub controller via the hub interconnect, andwherein the hub controller is configured to transmit the nurse callsoftware update to the nurse call interface circuit via an intrahubcommunication link.
 23. The nurse call system of claim 22, wherein thenurse call software update is a nurse call firmware update.
 24. Thenurse call system of claim 22, wherein the nurse call interface circuitcomprises a nurse call memory unit, and the nurse call interface circuitis configured to load the nurse call software update into the nurse callmemory unit.
 25. The nurse call system of claim 24, wherein the nursecall interface circuit is configured to load the nurse call softwareupdate into the nurse call memory unit only if the nurse call softwareupdate has been verified as genuine.
 26. The nurse call system of claim24, wherein the nurse call interface circuit further comprises a nursecall memory recovery module configured to load a previous nurse callsoftware version into the nurse call memory unit if the nurse callsoftware update fails to load.
 27. The nurse call system of claim 24wherein the PID is configured to produce a confirmation sound when thenurse call software update is successfully programmed into the nursecall memory unit.
 28. The nurse call system of claim 27, wherein theconfirmation sound is produced by an audio speaker.
 29. The nurse callsystem of claim 24, wherein the PID is configured to display aconfirmation notice the nurse call software updated is successfullyprogrammed into the nurse call memory unit.
 30. The nurse call system ofclaim 29, wherein the confirmation notice is shown by a display screen.31. The nurse call system of claim 22, wherein the PID is a pillowspeaker.